Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1422

reference: 584-tree-1
name: 1422
tree-preservation-order: undefined
584-tpo-1
uprn
address-text
point: POINT (-1.043195 50.868793)
geometry: MULTIPOLYGON (((-1.043139 50.868787,-1.043141 50.868798,-1.043149 50.868808,-1.043162 50.868816,-1.043177 50.868822,-1.043195 50.868824,-1.043212 50.868822,-1.043228 50.868817,-1.043241 50.868809,-1.043249 50.868799,-1.043252 50.868788,-1.043250 50.868777,-1.043242 50.868767,-1.043230 50.868759,-1.043214 50.868754,-1.043196 50.868752,-1.043179 50.868753,-1.043163 50.868758,-1.043150 50.868766,-1.043142 50.868776,-1.043139 50.868787)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL